Consolidate location of build products #19
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ChrisThrasher
force-pushed
the
output_directory
branch
from
d933baf
to
6743281
Compare
eXpl0it3r
approved these changes
Sep 7, 2023
|
I checked the CI logs and can see everything is put in build/bin/Release. Because MSBuild is a multi-config generator then it's inevitable there will be another directory inside bin/ corresponding to the current build type/config. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will make it easier to tell users where they're executable lives. Without this the location of the executables prone to change per OS. I'd like to tell users "you can find the app in build/bin".
This also has the benefit of ensuring all DLLs are consolidated in the same place which lets us remove some code.